Auto-Generated Summary

> Provide an extensive summary of the agreements by topic. No need to mention CRs.

The document provides extensive details on agreements and discussions related to Non-Terrestrial Networks (NTN) for NR Phase 3, Internet of Things (IoT) Phase 3, and IoT-NTN TDD mode. Below is a summarized breakdown of the agreements by topic:

NR-NTN Downlink Coverage Enhancements

1. SS/PBCH Periodicity:
• Support extended periodicity of 160ms for SS/PBCH blocks during initial access.
• Legacy UEs may not camp on cells with periodicity larger than 160ms.
2. PDCCH Repetition:
• Support inter-slot repetition for Type-0 PDCCH CSS.
• Repeated PDCCH candidates share the same aggregation level, coded bits, and candidate index.
• Options for enabling/disabling repetition include reserved bits in PBCH payload or implicit signaling.
3. PDSCH Enhancements:
• Support PDSCH repetition for SIB1 within the same slot as Type-0 PDCCH repetition.
• Msg4 PDSCH repetition supported with repetition factors of 2 and 4, using RV cycling.
4. Backward Compatibility:
• Legacy UEs may decode PDCCH and associated PDSCH in one slot and skip monitoring in the other slot.

Support of RedCap and eRedCap UEs with NR NTN Operating in FR1-NTN Bands

1. Collision Handling:
• Collision case 3 (semi-statically configured DL reception collides with UL transmission):
• Default priority rule: DL is prioritized unless overridden by network signaling.
• Collision case 4 (dynamically scheduled DL reception collides with UL transmission):
• Handling left to UE implementation for certain cases; network can override priority via RRC signaling.
2. RRC Parameters:
• UE-specific RRC parameters used to indicate UL overriding DL for applicable use cases.

NR-NTN Uplink Capacity/Throughput Enhancements

1. OCC (Orthogonal Cover Code) Design:
• OCC length and sequence configured by RRC higher layers.
• RV cycling applied across OCC groups.
• UE required to maintain phase continuity and power consistency for the duration of one OCC group.
2. Handling Overlaps:
• Legacy rules for UCI multiplexing or prioritization for dropping PUSCH/PUCCH apply with updates for OCC groups.
3. Dynamic Configuration:
• OCC sequence dynamically indicated via DCI.

IoT-NTN Uplink Capacity/Throughput Enhancements

1. OCC for NPUSCH Format 1:
• Support OCC length 2 for 3.75kHz and 15kHz SCS.
• Dynamic activation/deactivation of OCC supported by DCI.
2. DMRS Patterns:
• Sequential mapping or dropping of samples for TDM DMRS slots.
• CDM DMRS symbols spread before OCC is applied.
3. RRC Parameters:
• New parameter npusch-OCC-Enabled introduced to enable OCC for NPUSCH format 1 single tone.

IoT-NTN TDD Mode

1. Frame Structure:
• Uplink transmission gaps do not apply.
• NPRACH periodicities of 90ms and 180ms supported; 40ms and 80ms are not.
2. DL/UL Subframes:
• DL gaps may not apply; further discussion on periodicities for NPDCCH monitoring.
• SIB1-NB dropped in non-D NB-IoT subframes.
3. Precompensation:
• UE adjusts time/frequency pre-compensation before each set of consecutive 8 uplink subframes.
• No pre-compensation gap needed before uplink bursts.
4. GNSS Measurement Gap:
• Options include no enhancement, starting at non-D/non-U subframes, or not applying GNSS gaps.

General Agreements

1. Specification Impact:
• Many agreements involve no specification impact or are deferred to RAN2/RAN4 for further discussion.
2. Dynamic Signaling:
• Dynamic signaling via DCI for OCC activation/deactivation and sequence index.
3. Backward Compatibility:
• Ensuring backward compatibility with legacy UEs is a recurring theme.

This summary captures the key agreements and discussions across the topics without mentioning specific CRs.